Endpoints-Equal names a function, with lambda list (A B):
Are A and B references to the identical endpoint URI pattern?
Note that URIs that are not ENDPOINTS-EQUAL to one another can still conflict with one another in URI space. A template could have a variable term which differs from the matching term (URI path element) in the other template, but creates an ambiguity between them (both could plausibly accept some subset of matching URIs). The simplest form is something like: /a/:x cv. /a/b --- it is perfectly possible that :x could be b, making /a/b ambiguous between the two URIs.
There are two possible cures for this bug; let's say, “avoidance” and “CLOS.” With the CLOS solution, the more specific (less variables) method would override, just as a more specific method overrides a less specific method in the default method combination method in CLOS. The alternative is to not permit such URI pairs to exist at all.
Neither solution has yet been implemented.
Defined in file src/endpoint.lisp.